Skip to content

feat(cli): accept the billing team role - #421

Merged
gregberge merged 1 commit into
mainfrom
claude/arg-511-cli-billing-role
Nov 19, 2026
Merged

gregberge merged 1 commit into
mainfrom
claude/arg-511-cli-billing-role

Conversation

@gregberge

Copy link
Copy Markdown
Member

Description

Adds the billing team role (ARG-511) to the CLI. A billing member is a member who also manages the team's plan, spend limit and invoices.

  • argos account member set-level --level billing and argos account invite create … --level billing are now accepted. Choices: owner, billing, member, contributor.
  • argos account update --default-user-level is unchanged (member | contributor): billing is not a valid default role.
  • @argos-ci/api-client: TeamUserLevel is now "owner" | "billing" | "member" | "contributor".
  • argos-cli skill: lists the four roles and says every role but contributor reaches every project.

Important

Draft until the API accepts billing. The server change (argos-ci/argos, branch claude/arg-511-billing-role-4f491b) is not merged or deployed yet. Before then, the API rejects --level billing.

How schema.ts was regenerated

https://api.argos-ci.com/v2/openapi.yaml does not include billing yet. To regenerate:

  1. Took the production spec. The committed schema.ts is byte-identical to what openapi-typescript generates from it today, so the starting point had no drift.
  2. Patched only components.schemas.TeamUserLevel to match the server branch: the billing enum value and the new description.
  3. Ran openapi-typescript (7.13.0, the repo's version) on it.

The resulting diff is 2 lines. Once the server is deployed, run pnpm --filter @argos-ci/api-client run build-schema-types before merging. It should produce no diff. If it does, the server's final wording changed.

Type of changes

enhancement

Verification

  • pnpm run build, check-types, lint, check-format: all pass.
  • @argos-ci/cli unit project: 15 files, 171 tests pass. @argos-ci/api-client: 28 tests pass. The CLI e2e project needs CI secrets (ARGOS_TOKEN, USER_ACCESS_TOKEN), so it was not run locally.
  • Ran the built CLI against a local stub API (ARGOS_API_BASE_URL):
    $ argos account member set-level 42 --level billing --account acme --json
    PATCH /v2/accounts/acme/members/42 {"level":"billing"}
    $ argos account invite create a@acme.dev b@acme.dev --level billing --account acme --json
    POST /v2/accounts/acme/invites {"members":[{"email":"a@acme.dev","level":"billing"},{"email":"b@acme.dev","level":"billing"}]}
    $ argos account member set-level 42 --level bogus …
    error: option '--level <level>' argument 'bogus' is invalid. Allowed choices are owner, billing, member, contributor.
    $ argos account update --default-user-level billing …
    error: option '--default-user-level <level>' argument 'billing' is invalid. Allowed choices are member, contributor.
    

Checklist

  • The commit message follows the Conventional Commits policy
  • Lint and unit tests pass locally
  • No new tests: the change is a value in a commander .choices list, already typed against the generated TeamUserLevel
  • Documentation updated (skills/argos-cli/SKILL.md)

🤖 Generated with Claude Code

`argos account member set-level` and `argos account invite create` now
accept `--level billing`. A billing member is a member who also manages
the team's plan, spend limit and invoices.

`account update --default-user-level` keeps `member | contributor`:
billing is not a valid default role.

Refs ARG-511

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gregberge gregberge added the enhancement New feature or request label Nov 16, 2026
@linear-code

linear-code Bot commented Nov 16, 2026

Copy link
Copy Markdown

ARG-511

@gregberge
gregberge requested a review from jsfez November 16, 2026 20:08
@gregberge
gregberge marked this pull request as ready for review November 19, 2026 14:08
@gregberge
gregberge merged commit eddbbae into main Nov 19, 2026
77 checks passed
@gregberge
gregberge deleted the claude/arg-511-cli-billing-role branch November 19, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant